Using the Language Extended Lexicon to Support Non-Functional Requirements Elicitation

Although Non-Functional Requirements (NFR) have been present in many software development methods, they have been faced as a second or even third class type of requirement, frequently hided inside notes and therefore frequently neglected or forgotten. Surprisingly, despite the fact that nonfunctional requirements (NFR) are among the most expensive and difficult to deal with [5] [12] [3][10], even today there are only a few works that focus on NFR as first class requirements (e.g. [7][8] [10]. Not so surprisingly, stakeholders’ demand for NFR has been continuously increasing. During 2001 edition of ICSE Mantis Chen from ACD System presented the 3 most important aspects for a software in the stakeholders’ point of view and the 3 most important one in the developers’ point of view. All the 6 were non-functional requirements. This work intends to show how we used the Language Extended Lexicon as a way of supporting initial NFR elicitation.